In-Game Sports Prediction Betting System

ABSTRACT

This invention relates to users competing at predicting occurrence that happen during a live sports event. Users buy credits, and enter a betting zone wherein a counter with round points starts to increase. When an incident happens, the users in the betting zone and hold the highest amount of round points wins. Thus, users are encouraged to foresee upcoming occurrence as early as possible, and enter the betting zone so as to gain as many round points as possible.

BACKGROUND OF THE INVENTION

The present invention relates to the field of real time sports betting, and audience interaction to any sports game which includes predictable occurrences.

This invention gives sports fans the opportunity to predict occurrences that happen during the event (such as a goal in a soccer match). Many sports fans believe they can predict such occurrence and with this application they can compete with friends and other users who try to do the same.

Currently there are several inventions in the field of real time sports betting. The most relevant to ours are:

WO2012088540A1—a patent application which presents a method that gives sports fans a way to interact during a sports event by betting on sub-events that are being created by an admin and broadcasted to their mobile devices. For example, this application could broadcast a question to the users' devices asking if the player batting in a baseball game will make a home run.

WO2013132293A1—a second patent application presents a method of letting the users predict sub-events during a sports match. In this invention the users predict that an occurrence is going to happen within a predefined time frame. For example, the user presses a button if he believes that a goal is going to happen in the next 30 seconds.

BRIEF SUMMARY OF THE INVENTION

Our invention offers a method to sports fans for predicting pre-defined occurrences during a sports match. The users can click a button and enter the betting zone whenever they feel that the occurrence is about to take place, and leave the betting zone when they feel that the occurrence is no longer about to take place. When a user enters the betting zone (1) his credits decrease constantly; (2) his round points increase constantly; (3) he is in a state of potentially being awarded if an occurrence will actually happen while he is in the betting zone.

TERMS

Occurrence—Occurrences are things that happen during an event. For example: an occurrence can be a goal in a soccer match.

Betting Zone—The Betting zone is the place that the users should be in when an incident happens. Only users that were in the betting zone get rewarded when an occurrence happens . In order to enter the betting zone, the user have to press on a button of the application.

Credits—Credits are being used in order to enter the betting zone. Users can obtain credits either by buying them, or by winning. When users enter the betting zone, their credits decrease constantly. Once out of credit, the users can no longer enter the betting zone.

Round Points—The round point is a parameter that checks who was the first user that forecasted the occurrence. When entering the betting zone, a clock with the users' round points starts to run. If an incident happens, the users that were in the betting zone are being sorted according to the amount of round points that they have, so that the user that has the highest amount of round points gets the first place.

DETAILED DESCRIPTION OF THE INVENTION

This invention is a system that allows people watching a sports match to bet during the matches by predicting the when pre-defined occurrences will happen.

The users predict the occurrences by entering and leaving a betting zone. If an occurrence took place while a user was in the betting zone, he is awarded.

Each user starts the game with a certain amount of credits. Whenever he is in the betting zone, his credits decrease constantly. If the user runs out of credits he can no longer enter the betting zone.

When entering the betting zone, a round points counter starts to increase. If an occurrence happens during that time, the users that were in the betting zone and have the highest amount of round points, win.

If a user who is in the betting zone, feels that the chance for an occurrence to happen is no longer high, he can leave the betting zone and stops losing credits.

The aim of this game is to reward users who are able to recognize a situation that will lead to an occurrence. The game gives incentives to the first users that foresaw an upcoming occurrence, pressed the button and entered the betting zone. The credit limitation encourages the user to enter the betting zone only when he believes that there is a true chance for an occurrence to happen, for otherwise he will run out of credits quickly and won't have a chance to catch other occurrences. For the limitation to be effective, a good amount of credits to play with in a soccer game could be 300 seconds. This amount of time covers 5.6% of the game, as a full game lasts 90 minutes, which equals 5,400 seconds.

The round point mechanism rewards the first users that foresaw the occurrence. Its easy to foresee the occurrence a few seconds before it takes place, but it takes skill, intuition and good knowledge of the game to foresee it earlier.

All the credits that are reduced from the users that enter the betting zone, move to a general pot. Whenever an occurrence takes place and there are winners, the pot is being divided between them, where the users with the highest amount of round points get the highest share from the pot, and so on.

How it Actually Works

The application works on client's devices, such as smartphones, tablets, or any other device that can carry the required software.

The client's devices communicate with a central server that holds all the data.

Whenever a user clicks on a button to enter the betting zone, his device sends a message to the server with all the needed details.

The server sends back a message to the client, and on the client's side two counters start counting: one for the round points that starts from zero and increases constantly, and the other for credits that starts from the amount of credits the user had before entering the betting zone and decreases constantly.

After entering the betting zone, the client's device shows an option to leave the betting zone. By choosing that option, the client sends a message to the server that contains the details of the betting zone that the user is leaving. After receiving the request to leave the betting zone, the server calculates the remaining credits of the user by comparing the time stamp on the two messages (the one the client sent when entering the betting zone, and the one he sent when leaving it)and sends back to the client the remaining credits. Sometimes, due to connection times, there are going to be differences between the time counted on the client's device to the time counted on the server, and in those cases the user will see its credits counter correcting itself to the number of credits that was sent by the server.

When the server gets a notification of a real occurrence from the actual match, it stores the details in its database and sends a message to all involved clients with the details of the occurrence, and the calculations of earned credits.

The server will do the calculation of the credits and the clients will get a message from the server that contains the details of the occurence, the exact number of credits left for them to play with and the amount of credits that they have earned—all calculated by the server.

The calculation of the remaining credits will be by comparing the time stamp from the messages that were received when the users entered the betting zone to the time stamp of the occurrence.

To calculate the pot, the server accumulates the number of credits that were deducted from users since the last occurrence that had winners. Whenever an occurrence take place, the pot is being cleared and split between the winners.

The credits that are being given to the users as a prize cannot be used to enter the betting zone in the same match—this in order to prevent that the winning users would have an disproportionate amount of credits to play with.

Optional Features Rooms

The room feature can be added to increase personalization to the game. With this feature, users can choose to play within certain rooms. When a user enters the betting zone within a certain room, his credits move to the personal pot of the room, and the whole competition is happening within the room. Whenever an incident with winners happens, the winners split the pot that was accumulated in their room.

Power

The power is another optional feature which allows the users to choose “how strong” they want to enter the betting zone. By selecting a power, they choose the speed of their credits decrement and the speed of their round points increment. Users who believes that there is a very good chance for an occurrence to happen, may enter the betting zone with high level of power. This way his round points counter will increase very fast and he will have more round points in a case of an occurrence. The other side of it is that his credits that will decrease faster.

Stop Loss

The stop loss allows the users to limit to the amount of credits they want to spend when they enter the betting zone. For example: a user will be able to choose to leave the betting zone automatically after spending 100 credits.

Multiple Betting zones

Another way to enrich the game experience is by giving the users several betting options. In soccer for example, users will be able to enter the betting zone of several occurrences such as: goal and corner. If a corner will happen for example, only users that were in the corner's betting zone will get awarded.

Another option is to allow the user to enter two betting zones simultaneously. For example, a user will be allowed to enter the betting zones of goal and corner. If one of those occurrences will happen while the user was in the betting zone of the occurrence that has happened, he will be awarded for it. The credit should decrease faster when a user is in the betting zones of two or more occurrences, and each occurrence should have its own round points counter.

Different occurrence types may have different impact on the speed of round points and credits counters. For example, betting on a corner, which is much more common than a goal, will either cause the credits counter to decrease faster, or the round points counter to increase slower,—or both.

Betting Zones of Players

In this version the user sees betting buttons for each player on the field. The user can choose who will score the next occurrence (goal, basket) by getting into the betting zone of that particular player. The user will have the option to get into the betting zones of several players at a time. Different players will make different impacts on the counters, for example a good player will cause the credits counter to decrease faster, or the round points counter to increase slower, or both.

DESCRIPTION OF THE DRAWINGS

Drawing #1—Soccer—Waiting Mode

Drawing #1 presents a Smartphone implementation for soccer. The round points counter (in the bottom with the blue background) shows zero because the user didn't press “Get In” yet and he is not in the betting zone. In the pot there are 27 credits now.

Drawing #2—Soccer—in the Betting Zone

Drawing #2 presents a Smartphone implementation for soccer, when a user already pressed “Get In” and he is in the betting zone. The round point's counter increases constantly (stands on 60), and the credits counter decreases constantly (stands on 377). In the pot there are 75 credits, so if an occurrence will happen in that particular moment all the winning users are going to split those 75 credits, and the users with more time credits will win a bigger share. The user can either wait for an occurrence to happen or press “Get Out” in order to stop the credits' decrement and leave the betting zone.

Drawing #3—Flow Chart

Drawing #3 presents a flow chart of the whole process.

-   -   #1—The user waits for something that could indicate that an         occurrence is going to happen.     -   #2—The user feels that the occurrence is close and presses the         button to enter the betting zone. When pressing, a message is         sent to the server with the client's details.     -   #3 and #4—When receiving the accept notification from the         server, two things happen on the client's device simultaneously:         the round points counter starts to increase and a the remaining         credits starts to decrease.     -   #5—The user is now in the betting zone.     -   There are three ways to leave the betting zone:         -   a. #6—When the client's remaining credits are finished—he             will leave the betting zone automatically.         -   b. #7—When the occurrence happens—the server sends a message             to the clients that the occurrence has happened, and             mentions the amount of credits earned and the new amount of             remaining credits.         -   c. #8—When the user believes that the chances for an             occurrence to happen are lower and he presses a button to             leave the betting zone. A message is being sent to the             server, and the server calculates and sends back the amount             of the user's remaining credits. 

1. A system, game or application in which users are trying to predict when a predefined occurrence occurs by entering and leaving a betting zone. While the user is in the betting zone, his credits decrease constantly. If the occurrence has happened while the user was in the betting zone, he will be awarded for it. When a user runs out of credits, he will automatically leave the betting zone.
 2. A system according to claim 1, where the implementation on the client's side of the system is on an electronic device such as: smartphones, tablets, smart-TV, game console, smart glasses, desktop computers or any other device that can carry the required software.
 3. A system according to claim 1, where the users are people watching sports events (soccer for example) and the occurrences they are expecting are occurrences that tend to happen during a sports match (for example, a goal).
 4. A system according to claim 1, where as long as the user is in the betting zone, his round points counter increases constantly. In case an occurrence takes place, the winners (users that are in the betting zone) are sorted according to the number of round points they have, where the user with the highest amount of round points gets the first place.
 5. A system according to claims 1 and 4 where a user that wins, gets an award that is tied to the number of round points he has.
 6. A system according to claim 1, where the credits that are being decreased while users are in the betting zone are being accumulated in a general pot. Whenever an occurrence happens, the pot will be split between the users that are in the betting zone at that time.
 7. A system according to claims 1, 4 and 6 where the pot is being split in direct proportion to the place that the user got, so that the user who got the first place will get the biggest share from the pot.
 8. A system according to claim 1, where the application is used as a betting game and the user can buy credits to play with and can cash out the credits he won.
 9. A system according to claim 1, where user can buy extra credits to play with during the game, up to a predefined limit
 10. A system according to claim 1, where the application is used for fun and no money is involved.
 11. A system according to claim 1, where the users can see in each moment how many users are in the betting zone.
 12. A system according to claim 1, where there are betting zones for several types of occurrences, for example: goal, corner and foul in a soccer game.
 13. A system according to claims 1 and 12, where users can enter several betting zones simultaneously and by doing so, their credits decrease accordingly. For example a user that entered the betting zone of goal and believes that there is a good chance also for a corner to happen, can enter also the corner's betting zone. By doing so, he will cause his credits to decrease faster.
 14. A system according to claim 1, where the users are divided into groups, and the groups compete against each other for the accumulated amount of points. For example, a competition between Arsenal's and Liverpool's fans.
 15. A system according to claims 1 and 4, where the users cannot use the credits they won in order to enter the betting zone in the same game.
 16. A system according to claims 1 and 4, where the operators of the application can choose to allow the users to use a part of the credits they won, in order to enter the betting zone in the same game. The number of credits that can be used to enter the betting zone should be limited.
 17. A system according to claims 1 and 4, where the users can constantly see the amount of round points of all the users that are in a betting zone.
 18. A system according to claim 1, where there are two or more users playing the game against each other.
 19. A system according to claim 1, where the game is being played by one user, without any connection to other users.
 20. A system according to claim 1, where each team or player has its own betting zone.
 21. A system according to claims 1 and 20, where each team or player has its own speed score. For example, entering the betting zone of a good player that has better chances to score will cause a slower increase in the round points.
 22. A system according to claims 1, 20 and 21, where the score rate of each player is determined by his historical performance on the field.
 23. A system according to claims 1, 20 and 21, where the score rate of the players is determined by the number of users that entered his betting zone.
 24. A system according to claims 1, 20 and 21, where instead of changing the speed of the increase of the round points, the rating of the player will have effect on the credit decrement rate. For example, in the betting zone of a good player, the credits will decrease faster.
 25. A system according to claims 1 and 20, where the user can bet on multiple players or teams at the same time.
 26. A system according to claims 1, 20 and 25, where betting on multiple players at the same time will cause the credits to decrease in a speed that is equivalent to the aggregated speed of those players.
 27. A system according to claims 1, 20 and 25 where each player has its own round points counter.
 28. A system according to claim 1, where the application software is hosted on the client's device.
 29. A system according to claim 1, where the application software is hosted on the servers, and being served on the browsers of the client's device.
 30. A system according to claim 1, where each entrance to the betting zone is being registered on the system's servers.
 31. A system according to claims 1 and 2, where each entrance to the betting zone is being registered on the client's device.
 32. A system according to claim 1, where whenever someone enters the betting zone, all the other users see it.
 33. A system according to claims 1 and 4, where the increment of round points is linear.
 34. A system according to claims 1 and 4, where the calculation of round points is exponential, meaning for each second that a user is in the betting zone he is granted with (n)^(x) round points, where x is a parameter that determines the speed of the round points counter.
 35. A system according to claims 1, 2 and 3 where the credits counter is being decreased linearly.
 36. A system according to claim 1, where the credits counter is being decreased exponentially.
 37. A system according to claim 1, where users can choose a room to play in. A room can be: sports bar, stadium or any type of group who wants to play against each other.
 38. A system according to claims 1 and 37, where a manager of a room can become affiliated with the system operator and get a share from the earning, derived from the users in their room.
 39. A system according to claims 1, 6 and 37, where each room has its own pot and all the credits that decrease from users in this room, go to the room's pot. When users from this room win, they split their room's pot.
 40. A system according to claims 1 and 4, where the counting of round points or credits is being done by the server and the clients receive the results of these calculations.
 41. A system according to claims 1 and 4, where some counting, round points or credits is being done on the client's side and the server gets a message with the results.
 42. A system according to claim 1, where the users can define the maximum amount of credits they agree to lose when entering the betting zone. Using this option, they will leave the betting zone automatically after the amount of credits had passed.
 43. A system according to claims 1 and 4, where users can choose the speed of the decrement of their credits and the increment of their round points when they are in the betting zone. The speed of the decrement of the credit should be correlated to the speed of the round points increment. For example, a user that sees a good chance for an occurrence to happen, can choose a high speed of round point increment and high speed of credits decrement.
 44. A system according to claims 1, 4 and 40, where the server clock is trying to imitate the client's clock, by sending a message from the server to the client and expecting a message back. Doing this several times will give an estimation to the connection time. The server will deduct this time from its clock and will give the user a closer result to the clocks that he saw on his device.
 45. A system according to claims 1 and 37, where users can switch between rooms during the game.
 46. A system according to claims 1 and 37, where users can enter the betting zone of several rooms simultaneously.
 47. A system according to claims 1 and 4, where the speed of the decrement of the credits and the increment of the round points is being determined dynamically.
 48. A system according to claims 1, 4 and 47, where the speed of the decrement of the credits and the increment of the round points is being determined according to the number of users that are in the betting zone. 